Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LeverageLp]: Update liquidation algorithm #646

Merged
merged 22 commits into from
Jul 15, 2024
Merged

[LeverageLp]: Update liquidation algorithm #646

merged 22 commits into from
Jul 15, 2024

Conversation

amityadav0
Copy link
Contributor

Description

  • Update liquidation algorithm
  • Add hooks on stablestake for interest rate

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

Deployment Notes

Are there any specific considerations to take into account when deploying these changes? This may include new dependencies, scripts that need to be executed, or any aspects that can only be evaluated in a deployed environment.

Screenshots and Videos

Please provide any relevant before and after screenshots by uploading them here. Additionally, demo videos can be highly beneficial in demonstrating the process.

@amityadav0
Copy link
Contributor Author

Adding more tests now

@amityadav0 amityadav0 marked this pull request as ready for review July 12, 2024 10:01
}

// Liquidate <1.1 positions
// Q: What will happen if there won't be enough liquidity to return to users(as health for some positions must be below 1) ? Do we need to fill the pool ?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@amityadav0 if we dont have enough liquidity in the Testnet pool, we can still close the position as those positions were mostly created for test purposes during the testing phase and as we were actively updating the module functionallities

@cosmic-vagabond cosmic-vagabond merged commit f44b203 into main Jul 15, 2024
2 checks passed
@cosmic-vagabond cosmic-vagabond deleted the opt branch July 15, 2024 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants